One Click 11/OneClick11.iso/Manuntencao/Reparo/SQL Server 2000 Security Tools 8/SQLCritUpdPkg_ENU.exe/SQLCritUpd/readme_SQLHotfix.txt

Text File | 2003-02-09 | 14.2 KB | 340 lines

*******************************************************************
     SQL Critical Update 3.0 for Microsoft« SQL Server 2000 and
     SQL ServerÖ 2000 Desktop Engine (MSDE 2000) Readme File
                         February 09, 2003
*******************************************************************
      ⌐ Microsoft Corporation 2003. All rights reserved.
*******************************************************************

Contents

1.0 Liability Disclaimer
2.0 Introduction
3.0 Requirements and Restrictions
4.0 Running SQL Critical Update
  4.1 Running SQL Critical Update Using the Default Options
  4.2 Command-Line Options
  4.3 Running SQL Critical Update On a Cluster
5.0 Reviewing the Log File
6.0 Events in the Application Log

*******************************************************************
1.0 Liability Disclaimer
*******************************************************************
Microsoft is providing SQL Critical Update to apply a hotfix to
computers that are vulnerable to the Slammer worm. This tool is
provided AS-IS, with no warranties of any kind, either express or
implied. You should evaluate and test the tool before using it in your
environment.

As a prerequisite to using this tool, you are required to accept the
EULA. The EULA, named License.txt, is in the root directory where you
downloaded the SQL Critical Update Package.

*******************************************************************
2.0 Introduction
*******************************************************************
SQL Critical Update (SQLHotfix_XXX.exe) is a tool that scans for local
instances of SQL Server 2000 or SQL Server 2000 Desktop Engine (MSDE
2000) that are vulnerable to the Slammer worm. If a vulnerable
instance is found, the tool replaces vulnerable files with the
appropriate updated files.

This tool is designed to patch the instances of the following versions
of SQL Server against the Slammer worm:

SQL Server 2000 (initial release)
SQL Server 2000 SP1
SQL Server 2000 SP2
MSDE 2000 (initial release)
MSDE 2000 SP1
MSDE 2000 SP2

However, for the latest serviceability and security improvements, we
recommend testing and then applying SP3. If you cannot apply SP3, we
recommend applying SP2 and then using this tool or the SQL Critical
Update Wizard.

You can run SQL Critical Update by itself. However, the SQL Critical
Update Wizard provides an easy-to-use interface to help detect,
disable, update, and re-enable vulnerable instances of SQL Server 2000
and MSDE 2000. You can also use SMS Deploy to run SQL Check and then
run SQL Critical Update to deploy SQL Critical Update on client
computers using SMS.

SQL Critical Update will update SQL Server 2000 or MSDE 2000 instances
that are the same language as the SQL Critical Update package you are
running. For example, if you run the English version of SQL Critical
Update, non-English instances are not fixed.

SQL Critical Update performs the following tasks:

* Evaluates same-language instances of SQL Server 2000 and MSDE 2000
on a computer for potential vulnerabilities.
* Creates backup copies of the vulnerable files being replaced. The
backup copies are saved in subfolders named Backup\<patch number>
under each folder where SQL Critical Update replaces files.
* Replaces the vulnerable files with updated copies and runs any
required database scripts against the SQL Server 2000 or MSDE 2000
instance being updated.
* Runs Servpriv.exe to apply a permissions-related patch on instances
of SQL Server 2000 SP2.
* Writes all actions to a log file at %windir%\SQLHotfix.

NOTE: SQL Critical Update works only if the ssnetlib.dll and
sqlservr.exe files exist for each instance of SQL Server 2000 or MSDE
2000 being fixed. If these files have been deleted or renamed, either
contact your Technical Account Manager or Application Development
Consultant or call the toll-free Microsoft antivirus hotline at (866)
PCSAFETY [[phone]].

NOTE: SQL Critical Update does not install SP3. It only updates
vulnerable files on instances of SQL Server 2000 and MSDE 2000. For
SQL Server 2000 (initial release) and SQL Server 2000 SP1, the version
number reported by @@VERSION does not change. For SQL Server 2000 SP2,
the version number is updated. The results of running SELECT @@VERSION
for SQL Server 2000 and MSDE 2000 are as follows:

SQL Server 2000: 8.00.194
SQL Server 2000 SP1: 8.00.384
SQL Server 2000 SP2 before SQL Critical Update: 8.00.534
SQL Server 2000 SP2 after SQL Critical Update: 8.00.679
SQL Server 2000 SP3: 8.00.760

*******************************************************************
3.0 Requirements and Restrictions
*******************************************************************
Permissions:
The user running SQL Critical Update must have permission to replace
files in the Program Files directory. This requires you to be an
Administrator on the computer where you run SQL Critical Update. If
you do not have these permissions, SQL Critical Update will fail
without creating a log file.

System Requirements:

* PC with Intel or compatible Pentium 166 MHz or higher processor
* Minimum of 64 MB of RAM (128 MB or more recommended)
* Microsoft Internet Explorer 5.0 or later
* VGA or higher resolution monitor
* Microsoft Mouse or compatible pointing device

Supported Operating Systems:

* Microsoft Windows 98
* Microsoft Windows ME
* Microsoft Windows NT Workstation 4.0 with Service Pack 5
  or later
* Windows NT Server 4.0 with Service Pack 5 or later
* Windows NT Server 4.0 Enterprise Edition with Service Pack 5
  or later
* Windows 2000 Professional
* Windows 2000 Server
* Windows 2000 Advanced Server
* Windows 2000 Datacenter Server
* Windows XP Professional
* Windows XP Home

Restrictions:

* SQL Critical Update runs on the local machine only. To deploy the
hotfix to clients on a network, use SMS Deploy.
* SQL Critical Update will fix vulnerabilities that it finds; it
cannot be used to simply disable an instance of SQL Server. Use SQL
Check to disable vulnerable instances.

*******************************************************************
4.0 Running SQL Critical Update
*******************************************************************
This section describes the options for running SQL Critical Update.
There are two options, a default installation option that runs when
you double-click the SQLHotfix_XXX.exe file and a command line option.
Command line options are described in section 4.2.

When complete, SQL Critical Update returns SQL Server services to the
state that they were in before you ran the tool.  SQL Critical Update
does support the ability to change the startup options for disabled
instances to either Automatic or Manual. For more information, see
Section 4.2 Command-Line Options.

You do not need to reboot the computer after running SQL Critical
Update.

*******************************************************************
4.1 Running SQL Critical Update Using the Default Options
*******************************************************************
To run SQL Critical Update in the default mode, you can double-click
SQLHotfix_XXX.exe from the location where you saved it.

SQL Critical Update will display progress and then report status to a
dialog box. SQL Critical Update will write a log file in the
%windir%\SQLHotfix folder when processing is complete.

SQL Critical Update displays progress differently depending on the
operating system:
* Windows 98 and Windows ME display separate progress dialogs that
will close when the updates are complete.
* Windows NT, Windows 2000, Windows XP display progress in the user
interface.

*******************************************************************
4.2 Command-Line Options
*******************************************************************
To run SQL Critical Update from the command line, use the following
syntax:

  SQLHotfix_<lang>.exe [/a][/q] [DISABLESTATUS= AUTO|MANUAL]
    [INSTANCENAME= <name>] [SAPWD= <password>]

Where <lang> is the language of the version you downloaded. Possible
language values are:

  chs - Simplified Chinese (language = 2052)
  cht - Traditional Chinese (language = 1028)
  enu - English (language = 1033)
  esn - Spanish (language = 3082 or 1034)
  frn - French (language = 1036)
  ger û German (language = 1031)
  ita û Italian (language = 1040)
  jpn û Japanese (language = 1041)
  kor û Korean (language = 1042)
  brz - Portuguese (Brazil) (language = 1046)
  dut - Dutch (Netherlands) (language = 1043)
  sve û Swedish (language = 1053)

Use SQL Scan (Sqlscan.exe) to identify the language version of any
instance of SQL Server 2000 or SDE 2000. SQL Scan is included in the
SQL Critical Update Kit. Information on using SQL Scan is located in
the readme_sqlscan.txt.

/a
The /a switch passes the subsequent options to the SQLHotfix_XXX.exe
program. If you run SQLHotfix_XXX.exe with command line parameters, /a
must be the first parameter.

/q
The /q switch will run the utility in silent mode; no user interface
is displayed..

DISABLESTATUS
The DISABLESTATUS option enables you to change the startup
configuration for the SQL Server instances IF the status is Disabled.
If you do not specify a value for DISABLESTATUS, the startup
configuration is left as Disabled. If the startup configuration is
Auto or Manual, the status remains the same after running SQL Critical
Update. DISABLESTATUS has no effect on the SQL Agent service.

INSTANCENAME (Windows 98 and Windows ME only)
The INSTANCENAME parameter enables you to specify the name of an
instance to patch. This parameter and the SAPWD parameter is required
on SQL Server 2000 SP2 instances running on Windows 98 and Windows ME.
If you do not supply the INSTANCENAME parameter with the SAPWD
parameter, instances of SQL Server 2000 SP2 on Windows 98 and Windows
ME are not patched. This is reported in the log file at
%windir%\SQLHotfix.

For the INSTANCENAME value, supply just the instance name, and not the
MSSQL$ prefix. For example, if the instance name in the services panel
is MSSQL$CS, the instance name is CS.

SAPWD (Windows 98 and Windows ME only)
The SAPWD parameter supplies the SA password for instances on Windows
98 and Windows ME.

EXAMPLES
This example runs SQL Critical Update and changes the service startup
configuration to AUTO if the service has been disabled:

  SQLHotfix_ENU.exe /a DISABLESTATUS=AUTO

This example performs the same tasks as above, but does not report
status information when it completes. This is the command used to
perform unattended installations for most configurations:

  SQLHotfix_ENU.exe /a /q DISABLESTATUS=AUTO

This example shows the necessary command-line options to run an
unattended installation of SQL Critical Update on instances of SQL
Server 2000 SP2 on the Windows 98 and Windows ME operating systems:

  SQLHotfix_ENU.exe /a /q INSTANCENAME=MyInstance SAPWD=MyPassword

If you run SQL Critical Update from the command line using the /wait
flag with the Start command, the command prompt will return only when
processing is complete. For example:

  Start /wait /a /q SQLHotfix_ENU.exe


*******************************************************************
4.3 Running SQL Critical Update On a Cluster
*******************************************************************
SQL Critical Update automatically enumerates each virtual server and
updates all instances on the node running SQL Critical Update. All
nodes should be online while running SQL Critical Update. The SQL
Server resource can be offline or online. SQL Critical Update will
return the SQL Server resource to its previous state.

To run SQL Critical Update on a cluster with one virtual server:
Run SQL Critical Update on the node that owns the SQL Server resource.
SQL Critical Update patches all nodes that are possible owners of the
virtual server.

To run SQL Critical Update on a cluster with multiple virtual servers:
1. Move the groups that contain all SQL Server resources to a single
node.
2. Run SQL Critical Update on that node.

Moving all the groups that contain SQL Server resources to a single
node is an optional step to make it easier to run SQL Critical Update.
If you cannot move all the groups that contain SQL Server resources to
a single node, run SQL Critical Update on each active node to ensure
each virtual server is patched.

Note: The DISABLESTATUS parameter has no effect on failover nodes.

Verify the results in the Sqlhotfix#.log located in
%windir%\SQLHotfix.


*******************************************************************
5.0 Reviewing the Log File
*******************************************************************
The log file contains information about the actions of SQL Critical
Update. You can view the log file in the %windir%\SQLHotfix directory.

The log file has detailed information about actions taken on each
instance. At the bottom of the log file, for each instance patched by
SQL Critical Update, the log contains the following report:

    INSTANCE NAME: <instance name>
    PATCH PACKAGE APPLIED: <version>
    INSTALL STATUS: SUCCESS

If SQL Critical Update fails, the following message will appear at the
bottom of the log file:

    Hotfix failed to apply the patch to at least one instance,
    inspect the log file completely for status on all instances

If no update is required, the following message will appear at the
bottom of the log file:

    HotfFix Installer did not find any installation or instance
    of SQL Server that qualifies for this hotfix"

*******************************************************************
6.0 Events in the Application Log
*******************************************************************
SQL Critical Update does not write events to the Application log.
However, when running this SQL Critical Update, you should expect to
see event 7031 from the Service Control Manager:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Description: The MSSQL$<InstanceName> service terminated
unexpectedly.  It has done this 1 time(s). The following corrective
action will be taken in 0 milliseconds: No action.